Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39bb9a5b77609a5699c45949e062ba1175ae130e95894b3e5463c5d5a0c309a9

Tx prefix hash: adaf5e1608414273388bef40cf48691baba52f9814f738bb5f14f2afe447ec87
Tx public key: 00183a40cb40e21ecfead53b39937d6ef07f9195c1a0ba0f005da9d9a9114ce1
Timestamp: 1701079132 Timestamp [UCT]: 2023-11-27 09:58:52 Age [y:d:h:m:s]: 01:170:14:49:43
Block: 900682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383131 RingCT/type: yes/0
Extra: 0100183a40cb40e21ecfead53b39937d6ef07f9195c1a0ba0f005da9d9a9114ce102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.644106889000 dcy

stealth address amount amount idx
00: 8936c2651d2a5f13add31e9abe76ce211b0c3816b0951d8bff1d2243e0ce8cfc 0.644106889000 1357195 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": 900692, "vin": [ { "gen": { "height": 900682 } } ], "vout": [ { "amount": 644106889, "target": { "key": "8936c2651d2a5f13add31e9abe76ce211b0c3816b0951d8bff1d2243e0ce8cfc" } } ], "extra": [ 1, 0, 24, 58, 64, 203, 64, 226, 30, 207, 234, 213, 59, 57, 147, 125, 110, 240, 127, 145, 149, 193, 160, 186, 15, 0, 93, 169, 217, 169, 17, 76, 225, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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