Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 883e8012ffc4d8fc0ff05432f06baaeb5c21f4b9bc93c6e04cacc84088f828df

Tx prefix hash: 4dcaf93848b8ce03446ca27a869cb3118ca6275f8b1a2a2a45b40a93bbca2eaf
Tx public key: 2b04e54f5e912b171fa0ed7d3d3b3122112c4d6d856c105675988b63b97eadb5
Timestamp: 1710698669 Timestamp [UCT]: 2024-03-17 18:04:29 Age [y:d:h:m:s]: 00:342:12:55:58
Block: 980464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244858 RingCT/type: yes/0
Extra: 012b04e54f5e912b171fa0ed7d3d3b3122112c4d6d856c105675988b63b97eadb502110000001059dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b0d3c5c898426d8d8998cba9d2de3f38402310d9d17ccc6e23b1ed3b606bc94 0.600000000000 1440531 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": 980474, "vin": [ { "gen": { "height": 980464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b0d3c5c898426d8d8998cba9d2de3f38402310d9d17ccc6e23b1ed3b606bc94" } } ], "extra": [ 1, 43, 4, 229, 79, 94, 145, 43, 23, 31, 160, 237, 125, 61, 59, 49, 34, 17, 44, 77, 109, 133, 108, 16, 86, 117, 152, 139, 99, 185, 126, 173, 181, 2, 17, 0, 0, 0, 16, 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