Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04359a5fa07926d6e954ed2adc75100c1601db2e050f84c460fea8505ce52c3a

Tx prefix hash: 81448bb93edb7e9131b15f0a36b97a5d6dbe8aeba807969f4fa0a1fac19d22ff
Tx public key: f95a9d632b36d0bd171bc0f4f822e371256ecd741610d2dd69c69becdc4a1421
Timestamp: 1720030143 Timestamp [UCT]: 2024-07-03 18:09:03 Age [y:d:h:m:s]: 00:333:02:57:53
Block: 1057803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238072 RingCT/type: yes/0
Extra: 01f95a9d632b36d0bd171bc0f4f822e371256ecd741610d2dd69c69becdc4a14210211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 606ccef4098d73b84ab8d5721c1b5674c25d5caccd0fdae8d1ee69a3df659c44 0.600000000000 1528244 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": 1057813, "vin": [ { "gen": { "height": 1057803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606ccef4098d73b84ab8d5721c1b5674c25d5caccd0fdae8d1ee69a3df659c44" } } ], "extra": [ 1, 249, 90, 157, 99, 43, 54, 208, 189, 23, 27, 192, 244, 248, 34, 227, 113, 37, 110, 205, 116, 22, 16, 210, 221, 105, 198, 155, 236, 220, 74, 20, 33, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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