Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a580edb24e9e22e9b8d1c728a00d7534b0ffb12211a79f8bd333d9288749eba

Tx prefix hash: 77a830d855d6fd44519a6db4ba5f3a4fb99ce50a2ee496f1559b8e5c757fc6c5
Tx public key: 569a13e8fc7213be91e928cc3bfc915b3eb8054d677f247028a15fc5d7a4dbcf
Timestamp: 1711749650 Timestamp [UCT]: 2024-03-29 22:00:50 Age [y:d:h:m:s]: 01:048:02:54:16
Block: 989174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295366 RingCT/type: yes/0
Extra: 01569a13e8fc7213be91e928cc3bfc915b3eb8054d677f247028a15fc5d7a4dbcf0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 081b0b66a1b4fce01e21652ae3677fdfa36aefdf2676e59dd8aa84aa1b5edf27 0.600000000000 1449469 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": 989184, "vin": [ { "gen": { "height": 989174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "081b0b66a1b4fce01e21652ae3677fdfa36aefdf2676e59dd8aa84aa1b5edf27" } } ], "extra": [ 1, 86, 154, 19, 232, 252, 114, 19, 190, 145, 233, 40, 204, 59, 252, 145, 91, 62, 184, 5, 77, 103, 127, 36, 112, 40, 161, 95, 197, 215, 164, 219, 207, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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