Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53438bfe458811d83c3b7b2977e4f9460c3cd33e77e952ee2e8f98217ce86a31

Tx prefix hash: 9c64532281a00999be958a26fc7abf5d81602757e7f4c175719fe4da67420b7f
Tx public key: f681fcea1530bf22a78efc827922bffd98201a72a30643e71f3b19a36e6ed7c1
Timestamp: 1648245619 Timestamp [UCT]: 2022-03-25 22:00:19 Age [y:d:h:m:s]: 02:250:09:21:29
Block: 466366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698465 RingCT/type: yes/0
Extra: 01f681fcea1530bf22a78efc827922bffd98201a72a30643e71f3b19a36e6ed7c10211000000114a0f5013000000000000000000

1 output(s) for total of 17.487837096000 dcy

stealth address amount amount idx
00: 0cde3e29143bdb57f54d3c78cf62a79454d65d6c3787dd859234369b56e794e1 17.487837096000 884669 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": 466376, "vin": [ { "gen": { "height": 466366 } } ], "vout": [ { "amount": 17487837096, "target": { "key": "0cde3e29143bdb57f54d3c78cf62a79454d65d6c3787dd859234369b56e794e1" } } ], "extra": [ 1, 246, 129, 252, 234, 21, 48, 191, 34, 167, 142, 252, 130, 121, 34, 191, 253, 152, 32, 26, 114, 163, 6, 67, 231, 31, 59, 25, 163, 110, 110, 215, 193, 2, 17, 0, 0, 0, 17, 74, 15, 80, 19, 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