Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56b30023c3981daa9128cca0bf57bc5c18a6ef71968f5242992526027d2949f0

Tx prefix hash: ff07e4942c60af91bc7cc40d7f5265e26ec613d2f7cccaee8745f828c7dc5a5d
Tx public key: dd4614bc3890a7b4e3f8bf638da619eebc1d1b58062efa55f6fcbc667143b3be
Timestamp: 1584920895 Timestamp [UCT]: 2020-03-22 23:48:15 Age [y:d:h:m:s]: 05:077:19:48:02
Block: 86810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1213314 RingCT/type: yes/0
Extra: 01dd4614bc3890a7b4e3f8bf638da619eebc1d1b58062efa55f6fcbc667143b3be021100000018e1f32f7d000000000000000000

1 output(s) for total of 316.492347349000 dcy

stealth address amount amount idx
00: e79645ad46dd61c4fe6474e63e639f4081e2e2c9e3fbe89c4b353939db951a58 316.492347349000 156622 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": 86820, "vin": [ { "gen": { "height": 86810 } } ], "vout": [ { "amount": 316492347349, "target": { "key": "e79645ad46dd61c4fe6474e63e639f4081e2e2c9e3fbe89c4b353939db951a58" } } ], "extra": [ 1, 221, 70, 20, 188, 56, 144, 167, 180, 227, 248, 191, 99, 141, 166, 25, 238, 188, 29, 27, 88, 6, 46, 250, 85, 246, 252, 188, 102, 113, 67, 179, 190, 2, 17, 0, 0, 0, 24, 225, 243, 47, 125, 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