Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ccbd677f9ef5142d37db64385a4d8077716e44f96fa81d77644bae74a517992

Tx prefix hash: d5620eaacb6b729b9d33cc433d24749f610051624dd49e7fc54e6a6f154d77cd
Tx public key: 0cc916da0718da4b196d2e5e2a5a9d0a9c85a40f9b6ae668048e2893b2e32537
Timestamp: 1675097677 Timestamp [UCT]: 2023-01-30 16:54:37 Age [y:d:h:m:s]: 02:119:09:51:10
Block: 686164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607022 RingCT/type: yes/0
Extra: 010cc916da0718da4b196d2e5e2a5a9d0a9c85a40f9b6ae668048e2893b2e3253702110000000233af99f4000000000000000000

1 output(s) for total of 3.269292373000 dcy

stealth address amount amount idx
00: 2f4a472f2cac1f4a2ab6b7a2a9595ee365d96a6045456cf725c678a0850e80f0 3.269292373000 1128633 of 0

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": 686174, "vin": [ { "gen": { "height": 686164 } } ], "vout": [ { "amount": 3269292373, "target": { "key": "2f4a472f2cac1f4a2ab6b7a2a9595ee365d96a6045456cf725c678a0850e80f0" } } ], "extra": [ 1, 12, 201, 22, 218, 7, 24, 218, 75, 25, 109, 46, 94, 42, 90, 157, 10, 156, 133, 164, 15, 155, 106, 230, 104, 4, 142, 40, 147, 178, 227, 37, 55, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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