Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14db70d3320b4dc1d8ec02e61995561e92b7f2bb74c281b0438e9e051619927f

Tx prefix hash: 74e34bd52a8dec62882fd1df294ed92a5944aa42f291f107c7fcbfec6b98f21d
Tx public key: 3bdfc20a429c83d4cefa0fd91a9eff69fbebe9f68fb493969aeca7979c7e25d3
Timestamp: 1712608883 Timestamp [UCT]: 2024-04-08 20:41:23 Age [y:d:h:m:s]: 00:323:03:38:27
Block: 996253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231029 RingCT/type: yes/0
Extra: 013bdfc20a429c83d4cefa0fd91a9eff69fbebe9f68fb493969aeca7979c7e25d302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbac4483e590a995ccc6ca520b5b465baa5c35c224e85ec386629bdded7c7392 0.600000000000 1456669 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": 996263, "vin": [ { "gen": { "height": 996253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbac4483e590a995ccc6ca520b5b465baa5c35c224e85ec386629bdded7c7392" } } ], "extra": [ 1, 59, 223, 194, 10, 66, 156, 131, 212, 206, 250, 15, 217, 26, 158, 255, 105, 251, 235, 233, 246, 143, 180, 147, 150, 154, 236, 167, 151, 156, 126, 37, 211, 2, 17, 0, 0, 0, 1, 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