Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14e0cedb69a75b9d19492ea7b6e80011326a4510db60cb5940226fa36e151016

Tx prefix hash: 916fb696429af1b2d123eeff8bd2942d905fe5335c7774ddcc02ede5dfdc69af
Tx public key: 5d22fb0cde8cce9c9b574c3fbf68595b5098a17fafd9a5e5f950de4f1db44a3d
Timestamp: 1700415668 Timestamp [UCT]: 2023-11-19 17:41:08 Age [y:d:h:m:s]: 01:201:14:30:56
Block: 895189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405309 RingCT/type: yes/0
Extra: 015d22fb0cde8cce9c9b574c3fbf68595b5098a17fafd9a5e5f950de4f1db44a3d021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.663540175000 dcy

stealth address amount amount idx
00: 6e078b8e0c5477e005e445a2d416193b242514efe9d1d584a9fe77b7ba821215 0.663540175000 1351412 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": 895199, "vin": [ { "gen": { "height": 895189 } } ], "vout": [ { "amount": 663540175, "target": { "key": "6e078b8e0c5477e005e445a2d416193b242514efe9d1d584a9fe77b7ba821215" } } ], "extra": [ 1, 93, 34, 251, 12, 222, 140, 206, 156, 155, 87, 76, 63, 191, 104, 89, 91, 80, 152, 161, 127, 175, 217, 165, 229, 249, 80, 222, 79, 29, 180, 74, 61, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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