Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bb4e4ec7a9d48719a07c84c1bda2407b5daa97fa5d6c760db8353a323f51322

Tx prefix hash: 279f9755945ee8a85ab7e63a265ef7d15e782fc2a21a050d5d3e48cbc71c2a54
Tx public key: 8a53eb226db3896afaf771e9f69f3a04aa70cfba6371ff9ed7129da802d35562
Timestamp: 1719671781 Timestamp [UCT]: 2024-06-29 14:36:21 Age [y:d:h:m:s]: 01:132:17:05:23
Block: 1054827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353391 RingCT/type: yes/0
Extra: 018a53eb226db3896afaf771e9f69f3a04aa70cfba6371ff9ed7129da802d355620211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec1d2352bb27bb3a8b68274033a33d917241f7b0b1c734abc2abc37b2fd0cc61 0.600000000000 1525218 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": 1054837, "vin": [ { "gen": { "height": 1054827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec1d2352bb27bb3a8b68274033a33d917241f7b0b1c734abc2abc37b2fd0cc61" } } ], "extra": [ 1, 138, 83, 235, 34, 109, 179, 137, 106, 250, 247, 113, 233, 246, 159, 58, 4, 170, 112, 207, 186, 99, 113, 255, 158, 215, 18, 157, 168, 2, 211, 85, 98, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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