Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967f09e1989dcd7ba2f007b861704d8b0e2a80081ca34278ab7dd53d7076de16

Tx prefix hash: f86ef1f0ba3a99c46b4a5698a3c27d3e813efd1bd85fdd4c08699f319b2fee73
Tx public key: ca9b56a667621f5de915f03a134f966ae36bb4ae82083855c1e8b66a76fc4d3d
Timestamp: 1726892534 Timestamp [UCT]: 2024-09-21 04:22:14 Age [y:d:h:m:s]: 01:047:11:39:05
Block: 1114699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292334 RingCT/type: yes/0
Extra: 01ca9b56a667621f5de915f03a134f966ae36bb4ae82083855c1e8b66a76fc4d3d02110000001d5a5c538d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08a46177da9c747f1c7daff49a8b1f78f2560aeb04dd1cc5e063463505414b0d 0.600000000000 1594572 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": 1114709, "vin": [ { "gen": { "height": 1114699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08a46177da9c747f1c7daff49a8b1f78f2560aeb04dd1cc5e063463505414b0d" } } ], "extra": [ 1, 202, 155, 86, 166, 103, 98, 31, 93, 233, 21, 240, 58, 19, 79, 150, 106, 227, 107, 180, 174, 130, 8, 56, 85, 193, 232, 182, 106, 118, 252, 77, 61, 2, 17, 0, 0, 0, 29, 90, 92, 83, 141, 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