Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b228dc2d48d436d3cc7413b65850cdbc5f8ddd42d889e43c283f0b24c2833e

Tx prefix hash: eaf6dc27dec6257d06aeb0976dd5004f8c0438ba095f4b5e33280a9a97698ad1
Tx public key: 87c14f151989bcd37dddd0bab2c6e01e20d81b7e66318518482d764f4e94853c
Timestamp: 1722457048 Timestamp [UCT]: 2024-07-31 20:17:28 Age [y:d:h:m:s]: 00:206:10:20:49
Block: 1077916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147400 RingCT/type: yes/0
Extra: 0187c14f151989bcd37dddd0bab2c6e01e20d81b7e66318518482d764f4e94853c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10daca4a2c8c3a5f0a400a6e6792e8d366ac5fd8e71c5edbc989631986db2070 0.600000000000 1550471 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": 1077926, "vin": [ { "gen": { "height": 1077916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10daca4a2c8c3a5f0a400a6e6792e8d366ac5fd8e71c5edbc989631986db2070" } } ], "extra": [ 1, 135, 193, 79, 21, 25, 137, 188, 211, 125, 221, 208, 186, 178, 198, 224, 30, 32, 216, 27, 126, 102, 49, 133, 24, 72, 45, 118, 79, 78, 148, 133, 60, 2, 17, 0, 0, 0, 5, 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