Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6f0d82ed054347cab578c5459c56a98a713fa452861a05a6d3a061a0de1ed75

Tx prefix hash: 499fbef6708e6ed10c4fc8a29f62f82733bb711abd7140e5774ff2460f930ff9
Tx public key: 3c88c97a9ed0b3ccf771adbec13f26c1910773bd53a567fb942ad84271066d7e
Timestamp: 1710264701 Timestamp [UCT]: 2024-03-12 17:31:41 Age [y:d:h:m:s]: 00:331:11:10:56
Block: 976854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236996 RingCT/type: yes/0
Extra: 013c88c97a9ed0b3ccf771adbec13f26c1910773bd53a567fb942ad84271066d7e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a69251c422617b61a74d2aae9c14480cb96bf4b73e3108e5f09946430d038d 0.600000000000 1436853 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": 976864, "vin": [ { "gen": { "height": 976854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a69251c422617b61a74d2aae9c14480cb96bf4b73e3108e5f09946430d038d" } } ], "extra": [ 1, 60, 136, 201, 122, 158, 208, 179, 204, 247, 113, 173, 190, 193, 63, 38, 193, 145, 7, 115, 189, 83, 165, 103, 251, 148, 42, 216, 66, 113, 6, 109, 126, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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