Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88e0751017531b99e0852f14bed2f26fffc9dafdcd70c8f98c7439f0f55a6c35

Tx prefix hash: 844eea80683d029e80325eb740fb304ae084fea52bee55cdb012169f08176d16
Tx public key: 662e6838d54580fb8b86bd8d5797e90c5781e58b570c7b9aabd836a52e77fa15
Timestamp: 1720506909 Timestamp [UCT]: 2024-07-09 06:35:09 Age [y:d:h:m:s]: 01:134:17:14:28
Block: 1061767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354800 RingCT/type: yes/0
Extra: 01662e6838d54580fb8b86bd8d5797e90c5781e58b570c7b9aabd836a52e77fa1502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f926715d5e1a95d816308efe98a9861d62dbaceff617d2585e9b848115eaf8b2 0.600000000000 1532262 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": 1061777, "vin": [ { "gen": { "height": 1061767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f926715d5e1a95d816308efe98a9861d62dbaceff617d2585e9b848115eaf8b2" } } ], "extra": [ 1, 102, 46, 104, 56, 213, 69, 128, 251, 139, 134, 189, 141, 87, 151, 233, 12, 87, 129, 229, 139, 87, 12, 123, 154, 171, 216, 54, 165, 46, 119, 250, 21, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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