Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb04fb4dd14a05be3382c489759f3d22e64d05a2aac1182902a03fccdc2f267

Tx prefix hash: a551cfc1cce57be7dbfe2851da24401715b9780fc114108c4f82cfe4fb7deb8f
Tx public key: 2edcf9655b3e818ee581c789ddf1bd752c8391a4aa2fca28a8a7683d1ffe3d10
Timestamp: 1732015934 Timestamp [UCT]: 2024-11-19 11:32:14 Age [y:d:h:m:s]: 00:139:15:53:31
Block: 1157081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99618 RingCT/type: yes/0
Extra: 012edcf9655b3e818ee581c789ddf1bd752c8391a4aa2fca28a8a7683d1ffe3d10021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 768f638f1f039ddf643d88b77780019ef813eb7502b3a93d4fbf19ab1323cb5d 0.600000000000 1642704 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": 1157091, "vin": [ { "gen": { "height": 1157081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "768f638f1f039ddf643d88b77780019ef813eb7502b3a93d4fbf19ab1323cb5d" } } ], "extra": [ 1, 46, 220, 249, 101, 91, 62, 129, 142, 229, 129, 199, 137, 221, 241, 189, 117, 44, 131, 145, 164, 170, 47, 202, 40, 168, 167, 104, 61, 31, 254, 61, 16, 2, 17, 0, 0, 0, 2, 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