Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9976b764beff61a342b3a069434a637df1d02c0abacfa6621e543e4a1e4ba7b

Tx prefix hash: 51d63f69bdfc39cbbb98d5e04bb5f16697631cc95058f82dff8a349c6ca6602d
Tx public key: dc0f295911f8a31255403e087067884db3c5795d092a0f12a8019548ac4108a2
Timestamp: 1719384329 Timestamp [UCT]: 2024-06-26 06:45:29 Age [y:d:h:m:s]: 00:151:07:26:28
Block: 1052445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108293 RingCT/type: yes/0
Extra: 01dc0f295911f8a31255403e087067884db3c5795d092a0f12a8019548ac4108a2021100000003d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59a1fc10ff92b7505e4e4ce6a4eec11b39b7d744eb3abd53237fe3c32ee3dfd1 0.600000000000 1522772 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": 1052455, "vin": [ { "gen": { "height": 1052445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59a1fc10ff92b7505e4e4ce6a4eec11b39b7d744eb3abd53237fe3c32ee3dfd1" } } ], "extra": [ 1, 220, 15, 41, 89, 17, 248, 163, 18, 85, 64, 62, 8, 112, 103, 136, 77, 179, 197, 121, 93, 9, 42, 15, 18, 168, 1, 149, 72, 172, 65, 8, 162, 2, 17, 0, 0, 0, 3, 215, 73, 245, 17, 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