Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae73c754183013e0a63eb0a7a97209f155981807ae8b2c93f39cdf75efe13c40

Tx prefix hash: 88ab18311a354e5f1954f21f587a64ce041cd8e71598956ef43efb9d8dd4432d
Tx public key: 69c01044e5101ab38f3917aa6ebb512da6f16df803a2180f5ae78109b96f5e31
Timestamp: 1712569628 Timestamp [UCT]: 2024-04-08 09:47:08 Age [y:d:h:m:s]: 01:002:22:49:26
Block: 995925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263094 RingCT/type: yes/0
Extra: 0169c01044e5101ab38f3917aa6ebb512da6f16df803a2180f5ae78109b96f5e3102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ded71dcc29e904f7c6edfdd835be49ad09530f30cf445afd089bef72fd34b215 0.600000000000 1456341 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": 995935, "vin": [ { "gen": { "height": 995925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ded71dcc29e904f7c6edfdd835be49ad09530f30cf445afd089bef72fd34b215" } } ], "extra": [ 1, 105, 192, 16, 68, 229, 16, 26, 179, 143, 57, 23, 170, 110, 187, 81, 45, 166, 241, 109, 248, 3, 162, 24, 15, 90, 231, 129, 9, 185, 111, 94, 49, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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