Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03aa47897494e889614ff37fb04ffa22558bec7ef21ab04caeaf32aeb93d89b

Tx prefix hash: 8283f2f21922cc032f99a213fa4dbc8e83bcac78f90cc9c31e04863e6df6193a
Tx public key: bd7c1c9bc70f872f74bc2b8eff939972d57315c2829d33fa8dc22bec89f9eed3
Timestamp: 1745350560 Timestamp [UCT]: 2025-04-22 19:36:00 Age [y:d:h:m:s]: 00:201:08:36:13
Block: 1267217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141619 RingCT/type: yes/0
Extra: 01bd7c1c9bc70f872f74bc2b8eff939972d57315c2829d33fa8dc22bec89f9eed30211000000116c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 357c2b39f9f227fd70dcdb881587c59f765c76fb69f46a7466663e1c8e40bae7 0.600000000000 1754444 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": 1267227, "vin": [ { "gen": { "height": 1267217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "357c2b39f9f227fd70dcdb881587c59f765c76fb69f46a7466663e1c8e40bae7" } } ], "extra": [ 1, 189, 124, 28, 155, 199, 15, 135, 47, 116, 188, 43, 142, 255, 147, 153, 114, 213, 115, 21, 194, 130, 157, 51, 250, 141, 194, 43, 236, 137, 249, 238, 211, 2, 17, 0, 0, 0, 17, 108, 152, 170, 61, 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