Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f841202c20ac7475f8707d64f5d74b67c0dbc4643556b946fa4f4db57a4f4b

Tx prefix hash: 5184694cf3b491b8de804026e1fbce48f6b9b2c0652089eb44ce0359b8acfd69
Tx public key: 8ca4aa93db389b01a7217ffc49b96220e040eda7fa8d785fef18960908541bd0
Timestamp: 1659478389 Timestamp [UCT]: 2022-08-02 22:13:09 Age [y:d:h:m:s]: 02:105:19:27:30
Block: 557383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597005 RingCT/type: yes/0
Extra: 018ca4aa93db389b01a7217ffc49b96220e040eda7fa8d785fef18960908541bd00211000000016570b1ef000000000000000000

1 output(s) for total of 8.732907534000 dcy

stealth address amount amount idx
00: 44b92783e328370d1b1a244d662f455661e57ae63a856658fd7c8c4b3908a36d 8.732907534000 989399 of 0

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": 557393, "vin": [ { "gen": { "height": 557383 } } ], "vout": [ { "amount": 8732907534, "target": { "key": "44b92783e328370d1b1a244d662f455661e57ae63a856658fd7c8c4b3908a36d" } } ], "extra": [ 1, 140, 164, 170, 147, 219, 56, 155, 1, 167, 33, 127, 252, 73, 185, 98, 32, 224, 64, 237, 167, 250, 141, 120, 95, 239, 24, 150, 9, 8, 84, 27, 208, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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