Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 371c97d42a1aa8805ae14107fa9dc6cbcb6aa4157dcdb5989ece43c6bab4ec2d

Tx prefix hash: be325b682183ee3ab5aede0a33e8cdc7be2d4ca32adcb91104b11979829c027a
Tx public key: 0eacf0b53ffea0cb8c4eeabbdb1e82a18c09f4b56ecb455c74912634e663a241
Timestamp: 1741862666 Timestamp [UCT]: 2025-03-13 10:44:26 Age [y:d:h:m:s]: 00:318:01:59:42
Block: 1238351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224967 RingCT/type: yes/0
Extra: 010eacf0b53ffea0cb8c4eeabbdb1e82a18c09f4b56ecb455c74912634e663a2410211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0001436f0075314cb86e5cd094844abb61ac8bd552adae3cd40c7c60b5819bf2 0.600000000000 1725310 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": 1238361, "vin": [ { "gen": { "height": 1238351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0001436f0075314cb86e5cd094844abb61ac8bd552adae3cd40c7c60b5819bf2" } } ], "extra": [ 1, 14, 172, 240, 181, 63, 254, 160, 203, 140, 78, 234, 187, 219, 30, 130, 161, 140, 9, 244, 181, 110, 203, 69, 92, 116, 145, 38, 52, 230, 99, 162, 65, 2, 17, 0, 0, 0, 7, 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