Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 8a38e1f7c81c4f73d8aa736b6b6603258f93fec03c171eb7d14d365b9a01f434

Tx prefix hash: 601bff4b2357d4b2b142a8b9f96e43ac1376bdc6358be08abeb8ec3a0db67321
Tx public key: 4098242e8b8f4977d531f8911d4fbee0df3f6b1707025dd4308330d6df77b23d
Timestamp: 1703312788 Timestamp [UCT]: 2023-12-23 06:26:28 Age [y:d:h:m:s]: 01:181:20:08:34
Block: 919213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390941 RingCT/type: yes/0
Extra: 014098242e8b8f4977d531f8911d4fbee0df3f6b1707025dd4308330d6df77b23d0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 580a4109cd2fc4e0c2dc125a2619c00ed4df37b4ddae40c2f2aba88b70bf4e7d 0.600000000000 1376879 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 919223, "vin": [ { "gen": { "height": 919213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "580a4109cd2fc4e0c2dc125a2619c00ed4df37b4ddae40c2f2aba88b70bf4e7d" } } ], "extra": [ 1, 64, 152, 36, 46, 139, 143, 73, 119, 213, 49, 248, 145, 29, 79, 190, 224, 223, 63, 107, 23, 7, 2, 93, 212, 48, 131, 48, 214, 223, 119, 178, 61, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8