Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 539e8ea8db9a5fb51fd4461c82e3a66867411ca383c0b683f6dbe38b68c00b2d

Tx prefix hash: 2942865d0c7ee3976ec2cd3978fda61e6b550c79ca4d3f6021df8a796ae25c7d
Tx public key: c4d5a1b4412dae3ee34aa1ab8a7226364115a2c0ddb6f710fd49c3d27e1ba697
Timestamp: 1712475301 Timestamp [UCT]: 2024-04-07 07:35:01 Age [y:d:h:m:s]: 01:213:14:41:38
Block: 995144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411361 RingCT/type: yes/0
Extra: 01c4d5a1b4412dae3ee34aa1ab8a7226364115a2c0ddb6f710fd49c3d27e1ba69702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e634573c1797720f16e0aabec92193b8593a9e0a70afa8f4a7d1e83f3e79089 0.600000000000 1455550 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": 995154, "vin": [ { "gen": { "height": 995144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e634573c1797720f16e0aabec92193b8593a9e0a70afa8f4a7d1e83f3e79089" } } ], "extra": [ 1, 196, 213, 161, 180, 65, 45, 174, 62, 227, 74, 161, 171, 138, 114, 38, 54, 65, 21, 162, 192, 221, 182, 247, 16, 253, 73, 195, 210, 126, 27, 166, 151, 2, 17, 0, 0, 0, 1, 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