Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 199e5c5f6822b28766f3dcd48bf4e7c6418cf93119279700a84c7470f91a9b79

Tx prefix hash: 74b284f3aa6b7ef83d0576d334467364d3180ed481e441a75661f6bba0d70ed0
Tx public key: 702977c9445d9fda3c0437cf95e41953c5fe517ff6fdd1baf88250f8ecc8c55e
Timestamp: 1702402448 Timestamp [UCT]: 2023-12-12 17:34:08 Age [y:d:h:m:s]: 01:140:04:47:21
Block: 911683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361325 RingCT/type: yes/0
Extra: 01702977c9445d9fda3c0437cf95e41953c5fe517ff6fdd1baf88250f8ecc8c55e02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1818bbee6588187023ceb3e5e1a6e45e3854e2fe5c7dd0eff8c328e13aa081f3 0.600000000000 1368899 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": 911693, "vin": [ { "gen": { "height": 911683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1818bbee6588187023ceb3e5e1a6e45e3854e2fe5c7dd0eff8c328e13aa081f3" } } ], "extra": [ 1, 112, 41, 119, 201, 68, 93, 159, 218, 60, 4, 55, 207, 149, 228, 25, 83, 197, 254, 81, 127, 246, 253, 209, 186, 248, 130, 80, 248, 236, 200, 197, 94, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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