Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd5e93e5ad27f52294293c48412dd6b069d1adb1ebd80f4a9d27087db68a1a41

Tx prefix hash: 977f47fe29d2254a4ffa74c1828d09d7a7dee7e87fa2ea4f02ee25eea7e7f47a
Tx public key: 24fbdefb8c35ec675048363aff6d7426183d4d24bc4602ae4de0b3100bd19584
Timestamp: 1721712613 Timestamp [UCT]: 2024-07-23 05:30:13 Age [y:d:h:m:s]: 00:185:19:04:17
Block: 1071746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132899 RingCT/type: yes/0
Extra: 0124fbdefb8c35ec675048363aff6d7426183d4d24bc4602ae4de0b3100bd19584021100000004e914dd15000000000000000000

1 output(s) for total of 0.615570000000 dcy

stealth address amount amount idx
00: 4ebc72dee47808c6ee9b64dda3d0c50c80096e49e1d01d7d32d1ed28515f29df 0.615570000000 1544085 of 0

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": 1071756, "vin": [ { "gen": { "height": 1071746 } } ], "vout": [ { "amount": 615570000, "target": { "key": "4ebc72dee47808c6ee9b64dda3d0c50c80096e49e1d01d7d32d1ed28515f29df" } } ], "extra": [ 1, 36, 251, 222, 251, 140, 53, 236, 103, 80, 72, 54, 58, 255, 109, 116, 38, 24, 61, 77, 36, 188, 70, 2, 174, 77, 224, 179, 16, 11, 209, 149, 132, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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