Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c21346dbfa62832aa3e110b792e145683f1c8103fa1bba20473f6ee573aa7a6

Tx prefix hash: c08a0c77521a6b71b6e65b4b3772e28ba28ceeec0708efd2c6f376945689aefc
Tx public key: 7ce0d2f81ca40c8db565233274d858f32ca0375c8ec8c429d4f099d7dbc74abe
Timestamp: 1704138068 Timestamp [UCT]: 2024-01-01 19:41:08 Age [y:d:h:m:s]: 01:090:12:15:45
Block: 926046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325800 RingCT/type: yes/0
Extra: 017ce0d2f81ca40c8db565233274d858f32ca0375c8ec8c429d4f099d7dbc74abe0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4b78f067b1597b3164fe3fa248afe1e6b68efdeeadd13671380ae63c8d5c4d5 0.600000000000 1383820 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": 926056, "vin": [ { "gen": { "height": 926046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4b78f067b1597b3164fe3fa248afe1e6b68efdeeadd13671380ae63c8d5c4d5" } } ], "extra": [ 1, 124, 224, 210, 248, 28, 164, 12, 141, 181, 101, 35, 50, 116, 216, 88, 243, 44, 160, 55, 92, 142, 200, 196, 41, 212, 240, 153, 215, 219, 199, 74, 190, 2, 17, 0, 0, 0, 5, 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