Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96d881853bf47738fdd4cc949774e5bd5075f34411e74f7b1d3da21d4ce17b8

Tx prefix hash: 959b0880624d0e42ddc02fb2e54550eeaf7ab3d8606bb1125a4b9df236558202
Tx public key: 1fed830b04ede57d2cfe72d34e2ab9b1e61ae914348523f93a1bb3cf81fd2046
Timestamp: 1706438396 Timestamp [UCT]: 2024-01-28 10:39:56 Age [y:d:h:m:s]: 01:282:05:43:08
Block: 945100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460503 RingCT/type: yes/0
Extra: 011fed830b04ede57d2cfe72d34e2ab9b1e61ae914348523f93a1bb3cf81fd204602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3363ad0be899fd91fcb93f7db4a4da038bd53d073f89b215c0b661f56a1fe4bc 0.600000000000 1403410 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": 945110, "vin": [ { "gen": { "height": 945100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3363ad0be899fd91fcb93f7db4a4da038bd53d073f89b215c0b661f56a1fe4bc" } } ], "extra": [ 1, 31, 237, 131, 11, 4, 237, 229, 125, 44, 254, 114, 211, 78, 42, 185, 177, 230, 26, 233, 20, 52, 133, 35, 249, 58, 27, 179, 207, 129, 253, 32, 70, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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