Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61fb0757ede769d581b3e9d631b2551d60b369fd0a1c45837a9df3553f03e12d

Tx prefix hash: 36ee5a5ed732c7dd5c8f10314f945fe228750d9b47f76304be73ba4f28d18c87
Tx public key: 396a319a0ef54bf449e8e2100e88a2d57eba47301c1f965cebcff9f74a573839
Timestamp: 1720977942 Timestamp [UCT]: 2024-07-14 17:25:42 Age [y:d:h:m:s]: 00:245:09:33:19
Block: 1065674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175301 RingCT/type: yes/0
Extra: 01396a319a0ef54bf449e8e2100e88a2d57eba47301c1f965cebcff9f74a573839021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e073b68adaf86eb90b1ad17a4cc3dc557e02b733d983b363567324aa0ba6d2 0.600000000000 1536223 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": 1065684, "vin": [ { "gen": { "height": 1065674 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e073b68adaf86eb90b1ad17a4cc3dc557e02b733d983b363567324aa0ba6d2" } } ], "extra": [ 1, 57, 106, 49, 154, 14, 245, 75, 244, 73, 232, 226, 16, 14, 136, 162, 213, 126, 186, 71, 48, 28, 31, 150, 92, 235, 207, 249, 247, 74, 87, 56, 57, 2, 17, 0, 0, 0, 20, 233, 20, 221, 21, 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