Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 167100a3eeb3c3beba95ca73347e2b03e43cdea94380d37db8e21f1a1703497e

Tx prefix hash: 20574b150fbca4fdfff495d2b5def3ac091b76f8fc1da1876ebbafcf55f8cffc
Tx public key: f4a9e6bf78ec0e183dbf858f15ae0970ce9cf5326b2fbdf2df174e1e1c37ba2a
Timestamp: 1745761051 Timestamp [UCT]: 2025-04-27 13:37:31 Age [y:d:h:m:s]: 00:240:18:55:51
Block: 1270616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169842 RingCT/type: yes/0
Extra: 01f4a9e6bf78ec0e183dbf858f15ae0970ce9cf5326b2fbdf2df174e1e1c37ba2a0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98c29842702490e6d53007f5a913256d058a255ab25fba3f2ec94738e15754d4 0.600000000000 1757859 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": 1270626, "vin": [ { "gen": { "height": 1270616 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98c29842702490e6d53007f5a913256d058a255ab25fba3f2ec94738e15754d4" } } ], "extra": [ 1, 244, 169, 230, 191, 120, 236, 14, 24, 61, 191, 133, 143, 21, 174, 9, 112, 206, 156, 245, 50, 107, 47, 189, 242, 223, 23, 78, 30, 28, 55, 186, 42, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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