Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d1c267a2e48d0aac96e3a03896acc7f051cd2e3cce8f0da439026cc80367d61

Tx prefix hash: 50f01c7850d9a50b5b66d635e1be2a76a5fdc41045fcd14adf9813a5ee56cb6a
Tx public key: 27d24af58c37a45a71824fd9971a0aba665d03223f8a8c6f2c1c2d336942fe57
Timestamp: 1701196607 Timestamp [UCT]: 2023-11-28 18:36:47 Age [y:d:h:m:s]: 01:343:01:21:52
Block: 901660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504054 RingCT/type: yes/0
Extra: 0127d24af58c37a45a71824fd9971a0aba665d03223f8a8c6f2c1c2d336942fe57021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.631576706000 dcy

stealth address amount amount idx
00: 94ccefae9739295754384db0ec71eda8dd124e1f748bb0178c4eb63f5ca3e7bd 0.631576706000 1358233 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": 901670, "vin": [ { "gen": { "height": 901660 } } ], "vout": [ { "amount": 631576706, "target": { "key": "94ccefae9739295754384db0ec71eda8dd124e1f748bb0178c4eb63f5ca3e7bd" } } ], "extra": [ 1, 39, 210, 74, 245, 140, 55, 164, 90, 113, 130, 79, 217, 151, 26, 10, 186, 102, 93, 3, 34, 63, 138, 140, 111, 44, 28, 45, 51, 105, 66, 254, 87, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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