Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc2a11972bffd15107d3fcca3a95b87c7e519efc4cae584d3507f099f47cc901

Tx prefix hash: 9bd63b9bb2f6f0c1badd70c52715c3a345fc47581756a004a325408e132f7d48
Tx public key: 27c0a3b12e14b1609940dd45213d71b3df10f28e257b24189386df5b7c9e8847
Timestamp: 1749868772 Timestamp [UCT]: 2025-06-14 02:39:32 Age [y:d:h:m:s]: 00:159:05:21:57
Block: 1304547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111558 RingCT/type: yes/0
Extra: 0127c0a3b12e14b1609940dd45213d71b3df10f28e257b24189386df5b7c9e88470211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb566040cbe0dc2e16633843bc5511cc6a4b6a750e86d36688717bea9b70d729 0.600000000000 1792138 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": 1304557, "vin": [ { "gen": { "height": 1304547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb566040cbe0dc2e16633843bc5511cc6a4b6a750e86d36688717bea9b70d729" } } ], "extra": [ 1, 39, 192, 163, 177, 46, 20, 177, 96, 153, 64, 221, 69, 33, 61, 113, 179, 223, 16, 242, 142, 37, 123, 36, 24, 147, 134, 223, 91, 124, 158, 136, 71, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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