Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d5fce0576227042c66ff03668318d248820eb5fb1e2dd98d7bfddd224792b45

Tx prefix hash: fe8a29f1964b3a6936dd25b9d82da7a6cf54f6a6f0fc4adf7bc3101e991b48f3
Tx public key: e9cd19116770a69f0f99ff97da0e3a8c750bb42545dddbd0026f3bd248b207fe
Timestamp: 1730488421 Timestamp [UCT]: 2024-11-01 19:13:41 Age [y:d:h:m:s]: 01:007:23:09:40
Block: 1144419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264126 RingCT/type: yes/0
Extra: 01e9cd19116770a69f0f99ff97da0e3a8c750bb42545dddbd0026f3bd248b207fe021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a615ac1b26f73b3d3f0abd338d335ee782525489868423cfdda92aa517d6ae1f 0.600000000000 1628636 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": 1144429, "vin": [ { "gen": { "height": 1144419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a615ac1b26f73b3d3f0abd338d335ee782525489868423cfdda92aa517d6ae1f" } } ], "extra": [ 1, 233, 205, 25, 17, 103, 112, 166, 159, 15, 153, 255, 151, 218, 14, 58, 140, 117, 11, 180, 37, 69, 221, 219, 208, 2, 111, 59, 210, 72, 178, 7, 254, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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