Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21887f5b6a15545560d294421fba2614258657a7d13567816af40526af7904c7

Tx prefix hash: 137ba899858cf4cc0d62651557bb3aa17a6580d2f74ed78149913a52ff259f8d
Tx public key: ae4c5d3740e2ea1a572fe18ee3e9a80ec1cce61e50245a51f35b87768b7ebeb9
Timestamp: 1740824998 Timestamp [UCT]: 2025-03-01 10:29:58 Age [y:d:h:m:s]: 00:261:12:33:10
Block: 1229736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184668 RingCT/type: yes/0
Extra: 01ae4c5d3740e2ea1a572fe18ee3e9a80ec1cce61e50245a51f35b87768b7ebeb90211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4200ed203340df1b91e2e5c0a32916f7e54e8bd15f623b1a1a8fa8b8aa93d29b 0.600000000000 1716625 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": 1229746, "vin": [ { "gen": { "height": 1229736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4200ed203340df1b91e2e5c0a32916f7e54e8bd15f623b1a1a8fa8b8aa93d29b" } } ], "extra": [ 1, 174, 76, 93, 55, 64, 226, 234, 26, 87, 47, 225, 142, 227, 233, 168, 14, 193, 204, 230, 30, 80, 36, 90, 81, 243, 91, 135, 118, 139, 126, 190, 185, 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