Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8e505cc7930ad5a0c84e1ca5611e7538b1202ee7cef5e8ef455f1b008691306

Tx prefix hash: 8453bbbb3429b63339bc87ec0c9b4b1afd2a78f0e3e32aa930c6a660e6871468
Tx public key: 1dc07e8e1decac9452c676a689d659dc5353a67424e7229fc5b59e59b8934f84
Timestamp: 1722357167 Timestamp [UCT]: 2024-07-30 16:32:47 Age [y:d:h:m:s]: 01:096:14:50:35
Block: 1077093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327540 RingCT/type: yes/0
Extra: 011dc07e8e1decac9452c676a689d659dc5353a67424e7229fc5b59e59b8934f84021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47276c0c321453d48be5e5aafeb31ce8154fad075a1d769cc39529dc9fcbbca9 0.600000000000 1549638 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": 1077103, "vin": [ { "gen": { "height": 1077093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47276c0c321453d48be5e5aafeb31ce8154fad075a1d769cc39529dc9fcbbca9" } } ], "extra": [ 1, 29, 192, 126, 142, 29, 236, 172, 148, 82, 198, 118, 166, 137, 214, 89, 220, 83, 83, 166, 116, 36, 231, 34, 159, 197, 181, 158, 89, 184, 147, 79, 132, 2, 17, 0, 0, 0, 5, 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