Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91299f65d183b7c5f2c8575e7b5aedf50da2544daadc2554a415d6a4a4df786

Tx prefix hash: 836fb6794ffdc01a9d2eb02db1fa1d5693c4ad50229cc1d8a65a33a03c3c953b
Tx public key: 8cb0d0dd95f0eb5fcf8d941d952c0cf8a1d2f9bee77b851814ff6582da90158a
Timestamp: 1685053153 Timestamp [UCT]: 2023-05-25 22:19:13 Age [y:d:h:m:s]: 01:277:01:05:21
Block: 768078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459180 RingCT/type: yes/0
Extra: 018cb0d0dd95f0eb5fcf8d941d952c0cf8a1d2f9bee77b851814ff6582da90158a02110000000175e3f0e9000000000000000000

1 output(s) for total of 1.750003504000 dcy

stealth address amount amount idx
00: 766f6f844b1fe64a303144a87b95fbc60b987e1e15349e0da2d953378e056a04 1.750003504000 1217257 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": 768088, "vin": [ { "gen": { "height": 768078 } } ], "vout": [ { "amount": 1750003504, "target": { "key": "766f6f844b1fe64a303144a87b95fbc60b987e1e15349e0da2d953378e056a04" } } ], "extra": [ 1, 140, 176, 208, 221, 149, 240, 235, 95, 207, 141, 148, 29, 149, 44, 12, 248, 161, 210, 249, 190, 231, 123, 133, 24, 20, 255, 101, 130, 218, 144, 21, 138, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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