Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 628fddf45087ed8c2c9ea1226d32724d1ee04804ce571529d0cbcb4025b62efe

Tx prefix hash: 977aa330be279f1b07a0659869f0f93aa0df19cfe895d4fef2a954fcc23357b9
Tx public key: cc1130f8d3cbcd1578ff5ebbfca0ae2557f5b982b83a6950387e50955132beb7
Timestamp: 1718206027 Timestamp [UCT]: 2024-06-12 15:27:07 Age [y:d:h:m:s]: 00:165:03:32:29
Block: 1042686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118190 RingCT/type: yes/0
Extra: 01cc1130f8d3cbcd1578ff5ebbfca0ae2557f5b982b83a6950387e50955132beb70211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beef8fc6f123583391858e61ba7b7eb11e8950b6d3dd037dbfc99dc2afcbef8c 0.600000000000 1511661 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": 1042696, "vin": [ { "gen": { "height": 1042686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beef8fc6f123583391858e61ba7b7eb11e8950b6d3dd037dbfc99dc2afcbef8c" } } ], "extra": [ 1, 204, 17, 48, 248, 211, 203, 205, 21, 120, 255, 94, 187, 252, 160, 174, 37, 87, 245, 185, 130, 184, 58, 105, 80, 56, 126, 80, 149, 81, 50, 190, 183, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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