Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b37305b34f5e86de9820dba62b8c313c312146a5f7f5008c6a6056789f6e4fd6

Tx prefix hash: cf968ec6ae81af65a728a29231fe61f6f77b6d7c81ddf4493aecc81f285670d6
Tx public key: d49b29c5687a6cb13c90dfbffffee6fc7f731c8c8d74b36b8680fa7215d725e6
Timestamp: 1702076237 Timestamp [UCT]: 2023-12-08 22:57:17 Age [y:d:h:m:s]: 01:038:06:02:06
Block: 908947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288707 RingCT/type: yes/0
Extra: 01d49b29c5687a6cb13c90dfbffffee6fc7f731c8c8d74b36b8680fa7215d725e6021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c097a6c11c1eca3b0fbeaf6ca928ae15d9e9f690e0965fd659451d7729b9b06a 0.600000000000 1366010 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": 908957, "vin": [ { "gen": { "height": 908947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c097a6c11c1eca3b0fbeaf6ca928ae15d9e9f690e0965fd659451d7729b9b06a" } } ], "extra": [ 1, 212, 155, 41, 197, 104, 122, 108, 177, 60, 144, 223, 191, 255, 254, 230, 252, 127, 115, 28, 140, 141, 116, 179, 107, 134, 128, 250, 114, 21, 215, 37, 230, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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