Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 050ff93464f2b86bd55f97b2909ae7b8409edf96de5a32463da7744ba3f9c00d

Tx prefix hash: 4e213145b7ffd96bbdf69403111befab1c78b93e0edf178a0ff75d3e9fc385ed
Tx public key: 40ef996a539d25fa72e67bff63713132c4c5cc964f4d27ea8c4e6028c285b122
Timestamp: 1736423077 Timestamp [UCT]: 2025-01-09 11:44:37 Age [y:d:h:m:s]: 00:346:18:37:31
Block: 1193574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245384 RingCT/type: yes/0
Extra: 0140ef996a539d25fa72e67bff63713132c4c5cc964f4d27ea8c4e6028c285b1220211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9a4c1b0f667870f196a3106ae8e5b6d1f0202a78e85adf3acbeccf0b0312430 0.600000000000 1680137 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": 1193584, "vin": [ { "gen": { "height": 1193574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9a4c1b0f667870f196a3106ae8e5b6d1f0202a78e85adf3acbeccf0b0312430" } } ], "extra": [ 1, 64, 239, 153, 106, 83, 157, 37, 250, 114, 230, 123, 255, 99, 113, 49, 50, 196, 197, 204, 150, 79, 77, 39, 234, 140, 78, 96, 40, 194, 133, 177, 34, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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