Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29650aa44b57aced28749ca6b75cacf12e89145f126ca8fd17ab3083ed16b12d

Tx prefix hash: c99795ee6117c01e7634af83b1c741cfd5b681a3c1a34c9c1459fbd0d69f0910
Tx public key: fef37d60e31fb376875ad52c82e8e77dde2bddd9d094307dfa80e752df4dec64
Timestamp: 1702041291 Timestamp [UCT]: 2023-12-08 13:14:51 Age [y:d:h:m:s]: 01:079:04:23:58
Block: 908662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317705 RingCT/type: yes/0
Extra: 01fef37d60e31fb376875ad52c82e8e77dde2bddd9d094307dfa80e752df4dec64021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14c9ed59723e5e16c52a6385ff0d5d2e9d15fbfe510a9375314f46d52f391ee9 0.600000000000 1365707 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": 908672, "vin": [ { "gen": { "height": 908662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14c9ed59723e5e16c52a6385ff0d5d2e9d15fbfe510a9375314f46d52f391ee9" } } ], "extra": [ 1, 254, 243, 125, 96, 227, 31, 179, 118, 135, 90, 213, 44, 130, 232, 231, 125, 222, 43, 221, 217, 208, 148, 48, 125, 250, 128, 231, 82, 223, 77, 236, 100, 2, 17, 0, 0, 0, 4, 250, 243, 92, 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