Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48ebd7127927cdc5610ddc4cbc2579ef12572d51134d2efe6becd0d30c1993c1

Tx prefix hash: 99e6c3df6c8f5da4cbed796e55c39c32b3ea200376c379a209b9717b304eaf4f
Tx public key: d4272e84f898853b2bfe60b996c0aec76a7ccbbdb03f64685a88db0e2fa2e7f9
Timestamp: 1760323228 Timestamp [UCT]: 2025-10-13 02:40:28 Age [y:d:h:m:s]: 00:082:10:13:14
Block: 1388738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59021 RingCT/type: yes/0
Extra: 01d4272e84f898853b2bfe60b996c0aec76a7ccbbdb03f64685a88db0e2fa2e7f90211000000045dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62798cb2cb6331a4216cde22edc0a43fa7ce34cfccd209aa3619843a17aa9986 0.600000000000 1876961 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": 1388748, "vin": [ { "gen": { "height": 1388738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62798cb2cb6331a4216cde22edc0a43fa7ce34cfccd209aa3619843a17aa9986" } } ], "extra": [ 1, 212, 39, 46, 132, 248, 152, 133, 59, 43, 254, 96, 185, 150, 192, 174, 199, 106, 124, 203, 189, 176, 63, 100, 104, 90, 136, 219, 14, 47, 162, 231, 249, 2, 17, 0, 0, 0, 4, 93, 251, 190, 42, 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