Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60fdf58aae3bda5a5497dd36a3a10c9da0f78a471e4c09bf4257d5c001d3fbbf

Tx prefix hash: 494b7f4f35c315620dfa604f7ae6b7f7d4fbd396a502f4c98b50e61623a409e9
Tx public key: 6cb37fa41dc96c8ef60e2cacb4164288b0727060fbcab4f19f781132a71426d9
Timestamp: 1702961882 Timestamp [UCT]: 2023-12-19 04:58:02 Age [y:d:h:m:s]: 01:068:13:50:39
Block: 916306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310096 RingCT/type: yes/0
Extra: 016cb37fa41dc96c8ef60e2cacb4164288b0727060fbcab4f19f781132a71426d9021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6f8787d1f5351d383aa4fd99f8da1994a4601a09775d7e1d32b243a7a9d12e4 0.600000000000 1373792 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": 916316, "vin": [ { "gen": { "height": 916306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6f8787d1f5351d383aa4fd99f8da1994a4601a09775d7e1d32b243a7a9d12e4" } } ], "extra": [ 1, 108, 179, 127, 164, 29, 201, 108, 142, 246, 14, 44, 172, 180, 22, 66, 136, 176, 114, 112, 96, 251, 202, 180, 241, 159, 120, 17, 50, 167, 20, 38, 217, 2, 17, 0, 0, 0, 3, 197, 69, 41, 96, 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