Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 404c8464ab07a373f6ca28ce12b61eeeed5e66f3968a4bb3d0c7e384d2776a1c

Tx prefix hash: 436045df423b0eb359997c38312f244a745dc3760af8b53bc56133a297faaf9c
Tx public key: 536fe772dabf48e032d10d2a620ed7f57b838e91dd4d3768e00a417b95ac843e
Timestamp: 1715561306 Timestamp [UCT]: 2024-05-13 00:48:26 Age [y:d:h:m:s]: 01:177:17:45:09
Block: 1020785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385602 RingCT/type: yes/0
Extra: 01536fe772dabf48e032d10d2a620ed7f57b838e91dd4d3768e00a417b95ac843e021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce76a5cb957c8c79e364814d7a67ed493f2859e8b1f7b5fbcca91f4b1955d554 0.600000000000 1484878 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": 1020795, "vin": [ { "gen": { "height": 1020785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce76a5cb957c8c79e364814d7a67ed493f2859e8b1f7b5fbcca91f4b1955d554" } } ], "extra": [ 1, 83, 111, 231, 114, 218, 191, 72, 224, 50, 209, 13, 42, 98, 14, 215, 245, 123, 131, 142, 145, 221, 77, 55, 104, 224, 10, 65, 123, 149, 172, 132, 62, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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