Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b573c6b79637f09d618e94255bf7aa4447f921a0e53556edf51b5c4a88cdf00

Tx prefix hash: 80645f2daa22f71892c8959b09d0c156e0a1c90a4fefc9a429bd3a5cadd867ac
Tx public key: 98faf4379875df47aef46e71f5963ea27f93523fbfea10449023849c1d5a2ff3
Timestamp: 1727422386 Timestamp [UCT]: 2024-09-27 07:33:06 Age [y:d:h:m:s]: 01:037:02:10:35
Block: 1119100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284881 RingCT/type: yes/0
Extra: 0198faf4379875df47aef46e71f5963ea27f93523fbfea10449023849c1d5a2ff302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cbd49c5b008e5981d84cdf6f834bf8ab6c7e7ad466c2320f3e1863742d01ee 0.600000000000 1600529 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": 1119110, "vin": [ { "gen": { "height": 1119100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cbd49c5b008e5981d84cdf6f834bf8ab6c7e7ad466c2320f3e1863742d01ee" } } ], "extra": [ 1, 152, 250, 244, 55, 152, 117, 223, 71, 174, 244, 110, 113, 245, 150, 62, 162, 127, 147, 82, 63, 191, 234, 16, 68, 144, 35, 132, 156, 29, 90, 47, 243, 2, 17, 0, 0, 0, 2, 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