Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 225049f985fd3613fa64c9627b2295b576654558c9127a08eb757589b13070f2

Tx prefix hash: 676d5f26f950ce03831c4aa85b3001c9a9017c2457f991f3864c9d83fab6d4d6
Tx public key: 5ba7d88468cf1c47b0ae321b0b0f17e965659c93121d5a1d91c44178000c2f7f
Timestamp: 1725037438 Timestamp [UCT]: 2024-08-30 17:03:58 Age [y:d:h:m:s]: 01:070:05:04:23
Block: 1099310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308626 RingCT/type: yes/0
Extra: 015ba7d88468cf1c47b0ae321b0b0f17e965659c93121d5a1d91c44178000c2f7f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5a66d8359c0396f11c9651186cf68b09f8a699247fa0388ac0199aa3db908c 0.600000000000 1575269 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": 1099320, "vin": [ { "gen": { "height": 1099310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5a66d8359c0396f11c9651186cf68b09f8a699247fa0388ac0199aa3db908c" } } ], "extra": [ 1, 91, 167, 216, 132, 104, 207, 28, 71, 176, 174, 50, 27, 11, 15, 23, 233, 101, 101, 156, 147, 18, 29, 90, 29, 145, 196, 65, 120, 0, 12, 47, 127, 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