Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2637a2109f878133a743f5086448310c3379cf514b491e884ffb55b4433659a

Tx prefix hash: 35f73d59fa3d85180d385af16eba79677cab15435b7da8befccfdf3b7ac730e3
Tx public key: bee0ac5bf6d5a41807492daa9335e63f4ca8d5f3157d245d261c9a6aac1ecdc9
Timestamp: 1748511228 Timestamp [UCT]: 2025-05-29 09:33:48 Age [y:d:h:m:s]: 00:172:23:43:51
Block: 1293401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121313 RingCT/type: yes/0
Extra: 01bee0ac5bf6d5a41807492daa9335e63f4ca8d5f3157d245d261c9a6aac1ecdc90211000000096a75b171000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1db6f5ce3d1af2149749809955c362c92cc47abe78862c0e29b2bb937d219236 0.600000000000 1780874 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": 1293411, "vin": [ { "gen": { "height": 1293401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1db6f5ce3d1af2149749809955c362c92cc47abe78862c0e29b2bb937d219236" } } ], "extra": [ 1, 190, 224, 172, 91, 246, 213, 164, 24, 7, 73, 45, 170, 147, 53, 230, 63, 76, 168, 213, 243, 21, 125, 36, 93, 38, 28, 154, 106, 172, 30, 205, 201, 2, 17, 0, 0, 0, 9, 106, 117, 177, 113, 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