Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d54a74f4ee326bf0b9e054dda563c947ea3bb7129c6d0ea27500310e0d4393

Tx prefix hash: c0883ca63436ad245565139eb9d0fbb321d91c6109629331da8b0f60815a1865
Tx public key: b7bba4d7b78c98808fb3216eb0d4c24cd72ba5dfc7f9faa0300f7d6492e40e78
Timestamp: 1733712389 Timestamp [UCT]: 2024-12-09 02:46:29 Age [y:d:h:m:s]: 00:104:16:16:07
Block: 1171141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74594 RingCT/type: yes/0
Extra: 01b7bba4d7b78c98808fb3216eb0d4c24cd72ba5dfc7f9faa0300f7d6492e40e78021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 471ed1d0af8a57e83248e4866810d77a2af0d00f0ddb0688e46b34abd2be2053 0.600000000000 1656878 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": 1171151, "vin": [ { "gen": { "height": 1171141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "471ed1d0af8a57e83248e4866810d77a2af0d00f0ddb0688e46b34abd2be2053" } } ], "extra": [ 1, 183, 187, 164, 215, 183, 140, 152, 128, 143, 179, 33, 110, 176, 212, 194, 76, 215, 43, 165, 223, 199, 249, 250, 160, 48, 15, 125, 100, 146, 228, 14, 120, 2, 17, 0, 0, 0, 4, 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