Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8236bd9a207eff9b14d250d5fc59dbe0142821cd6087ed8a990b06a8cc5f0888

Tx prefix hash: a432f9ee1de2a8817b55eefbe33be39c83d9e5b27a13e9febbdb93ea2423a4b1
Tx public key: 6ecefd8aae5fee0da1231a7b97627016c9534176d1e3f90ccbe16855f1a8757b
Timestamp: 1737094471 Timestamp [UCT]: 2025-01-17 06:14:31 Age [y:d:h:m:s]: 00:152:17:39:40
Block: 1199124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108852 RingCT/type: yes/0
Extra: 016ecefd8aae5fee0da1231a7b97627016c9534176d1e3f90ccbe16855f1a8757b021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7eb123907d6cb1b3f91032b3939ed1b3220de9b0bbf06f8f654a77418be6206 0.600000000000 1685753 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": 1199134, "vin": [ { "gen": { "height": 1199124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7eb123907d6cb1b3f91032b3939ed1b3220de9b0bbf06f8f654a77418be6206" } } ], "extra": [ 1, 110, 206, 253, 138, 174, 95, 238, 13, 161, 35, 26, 123, 151, 98, 112, 22, 201, 83, 65, 118, 209, 227, 249, 12, 203, 225, 104, 85, 241, 168, 117, 123, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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