Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d57c06be6495a5a287d8db7627160b7055b23d11e3ec693e12d43de1e651f93f

Tx prefix hash: 0f0788804c56320177e054c3088ee3d1ffc27cacffee333fad7b6bb0ad5c549d
Tx public key: a9cf49d1840bc11504e810c398242ff15c2f30360024885a320a55b0cee63d3c
Timestamp: 1735222420 Timestamp [UCT]: 2024-12-26 14:13:40 Age [y:d:h:m:s]: 00:088:20:51:55
Block: 1183654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63279 RingCT/type: yes/0
Extra: 01a9cf49d1840bc11504e810c398242ff15c2f30360024885a320a55b0cee63d3c02110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9c2a60c570f5d3bcd085f82994acf8625d999126d6a40d047739cc02928a9d1 0.600000000000 1670101 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": 1183664, "vin": [ { "gen": { "height": 1183654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9c2a60c570f5d3bcd085f82994acf8625d999126d6a40d047739cc02928a9d1" } } ], "extra": [ 1, 169, 207, 73, 209, 132, 11, 193, 21, 4, 232, 16, 195, 152, 36, 47, 241, 92, 47, 48, 54, 0, 36, 136, 90, 50, 10, 85, 176, 206, 230, 61, 60, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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