Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646afb03e9fa4e941ff38f03db0e2ca92b9d3c921f447a52a3d3d3c3adecf5a1

Tx prefix hash: 587a117d08ce5fe814e4e4757a967c021b0f5c11099c778931057adb8ebdfaff
Tx public key: f68e5b7af209a60d8a0b6a75bfeb91c9cd8f9de70ce43d746ff88f4dff015a7b
Timestamp: 1713042231 Timestamp [UCT]: 2024-04-13 21:03:51 Age [y:d:h:m:s]: 01:205:20:37:04
Block: 999854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405793 RingCT/type: yes/0
Extra: 01f68e5b7af209a60d8a0b6a75bfeb91c9cd8f9de70ce43d746ff88f4dff015a7b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13f5d8177c70cf4ba507fe6b9427c896929fd208a2dc916e5e70b8b885a15e0c 0.600000000000 1460342 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": 999864, "vin": [ { "gen": { "height": 999854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13f5d8177c70cf4ba507fe6b9427c896929fd208a2dc916e5e70b8b885a15e0c" } } ], "extra": [ 1, 246, 142, 91, 122, 242, 9, 166, 13, 138, 11, 106, 117, 191, 235, 145, 201, 205, 143, 157, 231, 12, 228, 61, 116, 111, 248, 143, 77, 255, 1, 90, 123, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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