Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93490b002969acc0af7ab556f21df3f87b6e505db7a0b92daae0d3f26dad439c

Tx prefix hash: 29912c76912e6ab1fc1da4689b2c2f8665648de813d9d41f288178c0ddc83aed
Tx public key: a6a4f09ab118cb44c4c857bb355b06ec5cfe8ab366f8aedef58e2dc81478df74
Timestamp: 1684919759 Timestamp [UCT]: 2023-05-24 09:15:59 Age [y:d:h:m:s]: 01:244:18:37:32
Block: 766977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 436336 RingCT/type: yes/0
Extra: 01a6a4f09ab118cb44c4c857bb355b06ec5cfe8ab366f8aedef58e2dc81478df7402110000000233af99f4000000000000000000

1 output(s) for total of 1.764765439000 dcy

stealth address amount amount idx
00: e160b270d5401901881f9984782357a294b530b33662d8ff4bd7c9918af1f939 1.764765439000 1216058 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": 766987, "vin": [ { "gen": { "height": 766977 } } ], "vout": [ { "amount": 1764765439, "target": { "key": "e160b270d5401901881f9984782357a294b530b33662d8ff4bd7c9918af1f939" } } ], "extra": [ 1, 166, 164, 240, 154, 177, 24, 203, 68, 196, 200, 87, 187, 53, 91, 6, 236, 92, 254, 138, 179, 102, 248, 174, 222, 245, 142, 45, 200, 20, 120, 223, 116, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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