Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4557e66ff52a0c457ee40f83b0a3cbd1697306d8afbb63b8e1ce75d2c462a0a1

Tx prefix hash: 3aaa4f1d584ed4b625a948ff5e0fa5b82f05d7072ff2a7d82c3ce64ef43510b0
Tx public key: 63cf5bd9cda57268aa9d164719bda5009daaaacd1aaf17dd615348209969db22
Timestamp: 1733903207 Timestamp [UCT]: 2024-12-11 07:46:47 Age [y:d:h:m:s]: 00:111:02:32:04
Block: 1172723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79185 RingCT/type: yes/0
Extra: 0163cf5bd9cda57268aa9d164719bda5009daaaacd1aaf17dd615348209969db22021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91fd5a476794b7fa813f812b791b746bf95dc9ee7ff76dea10d715a8d84e8f5a 0.600000000000 1658652 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": 1172733, "vin": [ { "gen": { "height": 1172723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91fd5a476794b7fa813f812b791b746bf95dc9ee7ff76dea10d715a8d84e8f5a" } } ], "extra": [ 1, 99, 207, 91, 217, 205, 165, 114, 104, 170, 157, 22, 71, 25, 189, 165, 0, 157, 170, 170, 205, 26, 175, 23, 221, 97, 83, 72, 32, 153, 105, 219, 34, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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