Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b582555447c659a6e6fab4a66a747857081b7c8e5e17446fd4ebb9439782fa7

Tx prefix hash: 9ca7032e6b4beb80af7d473dacfb416439d1d6676eca1c1a42b11242cce1e97b
Tx public key: 52910e775bd5e1a23fbf29d78c5940eaa05702f478cd0c2dc7d223702e57c79c
Timestamp: 1581093329 Timestamp [UCT]: 2020-02-07 16:35:29 Age [y:d:h:m:s]: 04:273:10:40:16
Block: 60741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086783 RingCT/type: yes/0
Extra: 0152910e775bd5e1a23fbf29d78c5940eaa05702f478cd0c2dc7d223702e57c79c02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 386.143004361000 dcy

stealth address amount amount idx
00: 63e0626e3b1b065880c4c35e6faff6bbd5fadd5c9b24d35ed56cacaf1e816d79 386.143004361000 111826 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": 60751, "vin": [ { "gen": { "height": 60741 } } ], "vout": [ { "amount": 386143004361, "target": { "key": "63e0626e3b1b065880c4c35e6faff6bbd5fadd5c9b24d35ed56cacaf1e816d79" } } ], "extra": [ 1, 82, 145, 14, 119, 91, 213, 225, 162, 63, 191, 41, 215, 140, 89, 64, 234, 160, 87, 2, 244, 120, 205, 12, 45, 199, 210, 35, 112, 46, 87, 199, 156, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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