Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bce23bdb4c0e6ee9eb71ebeca4a4dbdc7ef8e9f2a6dc8c75d7e69070b28291c1

Tx prefix hash: 5d66ec18404e60ab250e477a64c55fb74aa908393b4340ac0e9181bca45fe6df
Tx public key: aae7807f0e180b6986f775cd5159bd191d232cb7fe1438035ea0b60fe775bc77
Timestamp: 1705308041 Timestamp [UCT]: 2024-01-15 08:40:41 Age [y:d:h:m:s]: 01:092:22:29:04
Block: 935733 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327526 RingCT/type: yes/0
Extra: 01aae7807f0e180b6986f775cd5159bd191d232cb7fe1438035ea0b60fe775bc770211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 281b1c795744cdc2c584a4ab148e435184e40a78e7aa0945942d0dc382300b06 0.600000000000 1393749 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": 935743, "vin": [ { "gen": { "height": 935733 } } ], "vout": [ { "amount": 600000000, "target": { "key": "281b1c795744cdc2c584a4ab148e435184e40a78e7aa0945942d0dc382300b06" } } ], "extra": [ 1, 170, 231, 128, 127, 14, 24, 11, 105, 134, 247, 117, 205, 81, 89, 189, 25, 29, 35, 44, 183, 254, 20, 56, 3, 94, 160, 182, 15, 231, 117, 188, 119, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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