Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e68610ff01238c318785abca32da0b425dccd866abb411c0bee971baeea1838b

Tx prefix hash: b77326f9d36d57f2feec50422785d0744cfce72092122355b294197158df1eca
Tx public key: 3ac53ed1f3dfd3d7d8f343aefb2ca563f9ab613a876215543105a51f6ed9081c
Timestamp: 1711894511 Timestamp [UCT]: 2024-03-31 14:15:11 Age [y:d:h:m:s]: 01:030:20:14:53
Block: 990376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282995 RingCT/type: yes/0
Extra: 013ac53ed1f3dfd3d7d8f343aefb2ca563f9ab613a876215543105a51f6ed9081c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 010e24905cc3b4072131de1e5e74cfc1941d3c5c5c6c231c10b33b74868034be 0.600000000000 1450698 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": 990386, "vin": [ { "gen": { "height": 990376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "010e24905cc3b4072131de1e5e74cfc1941d3c5c5c6c231c10b33b74868034be" } } ], "extra": [ 1, 58, 197, 62, 209, 243, 223, 211, 215, 216, 243, 67, 174, 251, 44, 165, 99, 249, 171, 97, 58, 135, 98, 21, 84, 49, 5, 165, 31, 110, 217, 8, 28, 2, 17, 0, 0, 0, 2, 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