Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b69151a33db0a7781b03f0f918c2249b1a988b2942ddbf3ca5d0a7f91835bfe

Tx prefix hash: 11a79c34e14d104b584a582005943fb7141d395f1a4099655c1a3363e49cbf62
Tx public key: 78cc19eeabbf5c097a83a9b1fc0c489758b23823ed9e90ebffffc518b72537a8
Timestamp: 1737041676 Timestamp [UCT]: 2025-01-16 15:34:36 Age [y:d:h:m:s]: 00:155:17:40:52
Block: 1198685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110964 RingCT/type: yes/0
Extra: 0178cc19eeabbf5c097a83a9b1fc0c489758b23823ed9e90ebffffc518b72537a8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef79adc8de82c8bceaf4f718002d1343c08b0f0de5aa8915885b3acf00f47edc 0.600000000000 1685310 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": 1198695, "vin": [ { "gen": { "height": 1198685 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef79adc8de82c8bceaf4f718002d1343c08b0f0de5aa8915885b3acf00f47edc" } } ], "extra": [ 1, 120, 204, 25, 238, 171, 191, 92, 9, 122, 131, 169, 177, 252, 12, 72, 151, 88, 178, 56, 35, 237, 158, 144, 235, 255, 255, 197, 24, 183, 37, 55, 168, 2, 17, 0, 0, 0, 4, 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