Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17656574978286ec3dc119625c9a0aa4f8b054c324291e6dca5f08963f723938

Tx prefix hash: a9fb59346c5b32cd96e091992496e0ffb17df490b32fc92fae68c269c7d09539
Tx public key: b9362c1a21758b3dad5c02012b4164df3a0b8a13c83fa6a8b5d532e689a8e4ae
Timestamp: 1670161544 Timestamp [UCT]: 2022-12-04 13:45:44 Age [y:d:h:m:s]: 02:080:21:39:26
Block: 645278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 579468 RingCT/type: yes/0
Extra: 01b9362c1a21758b3dad5c02012b4164df3a0b8a13c83fa6a8b5d532e689a8e4ae02110000000183600029000000000000000000

1 output(s) for total of 4.466076026000 dcy

stealth address amount amount idx
00: c6a0af63bf85f6f79a9900fac0ef31eab3ebabb464b34b1b0d3ccb98371f39bd 4.466076026000 1085431 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": 645288, "vin": [ { "gen": { "height": 645278 } } ], "vout": [ { "amount": 4466076026, "target": { "key": "c6a0af63bf85f6f79a9900fac0ef31eab3ebabb464b34b1b0d3ccb98371f39bd" } } ], "extra": [ 1, 185, 54, 44, 26, 33, 117, 139, 61, 173, 92, 2, 1, 43, 65, 100, 223, 58, 11, 138, 19, 200, 63, 166, 168, 181, 213, 50, 230, 137, 168, 228, 174, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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