Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0124e9888dadd575a6f33dff7b833902eba5c87922e43d688644d537d20547

Tx prefix hash: 505a8df604338b7dbcd134bebec1c40d5e6e8cee2a8af79056c6e32cab01245b
Tx public key: bd08c9e5b0888f203f65e10f00db3f58bccf6d6e5a8f647678a76802528b5b39
Timestamp: 1711077227 Timestamp [UCT]: 2024-03-22 03:13:47 Age [y:d:h:m:s]: 01:020:08:55:18
Block: 983600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275531 RingCT/type: yes/0
Extra: 01bd08c9e5b0888f203f65e10f00db3f58bccf6d6e5a8f647678a76802528b5b390211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f348351da303920cb0322f4e877bec18672f1cfe303c4843c7b43f4ba591ced9 0.600000000000 1443741 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": 983610, "vin": [ { "gen": { "height": 983600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f348351da303920cb0322f4e877bec18672f1cfe303c4843c7b43f4ba591ced9" } } ], "extra": [ 1, 189, 8, 201, 229, 176, 136, 143, 32, 63, 101, 225, 15, 0, 219, 63, 88, 188, 207, 109, 110, 90, 143, 100, 118, 120, 167, 104, 2, 82, 139, 91, 57, 2, 17, 0, 0, 0, 4, 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