Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588adb8665f7a24d66a03e4d4c9248531021599747173b07966a824b8fda425a

Tx prefix hash: 7a4b630291023bc1e8d9427c5a687595f9586f00e4e3a45910889a894f0a5520
Tx public key: e40223347392ad05fd79f2db506d8dd0a8efca7657ce07a6a72ddb46aa01b6f9
Timestamp: 1577792791 Timestamp [UCT]: 2019-12-31 11:46:31 Age [y:d:h:m:s]: 04:331:20:35:41
Block: 35695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126301 RingCT/type: yes/0
Extra: 01e40223347392ad05fd79f2db506d8dd0a8efca7657ce07a6a72ddb46aa01b6f90211000000694fb58672000000000000000000

1 output(s) for total of 467.442828513000 dcy

stealth address amount amount idx
00: 3e0ca5c96d7f98f5e06e49d17cd5ba25494b0a5137e0c2706d2f5defba3f6e42 467.442828513000 60268 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": 35705, "vin": [ { "gen": { "height": 35695 } } ], "vout": [ { "amount": 467442828513, "target": { "key": "3e0ca5c96d7f98f5e06e49d17cd5ba25494b0a5137e0c2706d2f5defba3f6e42" } } ], "extra": [ 1, 228, 2, 35, 52, 115, 146, 173, 5, 253, 121, 242, 219, 80, 109, 141, 208, 168, 239, 202, 118, 87, 206, 7, 166, 167, 45, 219, 70, 170, 1, 182, 249, 2, 17, 0, 0, 0, 105, 79, 181, 134, 114, 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