Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 086c3cffce57b397de5ba71a28558f020bdc123622579c1449d5dc8b5e6aa1f2

Tx prefix hash: f5f12e120aed4255fa8eb48649b8c5bc38fda1fd1ff2b61f6e28657bc1d2bf52
Tx public key: cd4a7218d6d6c9c50d39e79fd967a7f052b311b386d992598ac21ff78bb79c37
Timestamp: 1748585891 Timestamp [UCT]: 2025-05-30 06:18:11 Age [y:d:h:m:s]: 00:164:13:27:31
Block: 1294006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115291 RingCT/type: yes/0
Extra: 01cd4a7218d6d6c9c50d39e79fd967a7f052b311b386d992598ac21ff78bb79c3702110000000643846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97914d6052b4928f6cd9bd68b07d399407a0aee634168d315180bd5f88a5f318 0.600000000000 1781501 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": 1294016, "vin": [ { "gen": { "height": 1294006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97914d6052b4928f6cd9bd68b07d399407a0aee634168d315180bd5f88a5f318" } } ], "extra": [ 1, 205, 74, 114, 24, 214, 214, 201, 197, 13, 57, 231, 159, 217, 103, 167, 240, 82, 179, 17, 179, 134, 217, 146, 89, 138, 194, 31, 247, 139, 183, 156, 55, 2, 17, 0, 0, 0, 6, 67, 132, 109, 102, 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