Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e56a8225c6452615cc841bf35405c92130792470230dfb0d95f6dc9d7e72b7a4

Tx prefix hash: 38bf3c8228976b529602d8c44a1bf72cebf01c394f78bcd982b49c6bd5cb57f4
Tx public key: e778535b9a837dd8c6dcb8f7db7be7f397c4a5960ad9a2da6dfdb301dc91679a
Timestamp: 1721614321 Timestamp [UCT]: 2024-07-22 02:12:01 Age [y:d:h:m:s]: 00:173:04:10:42
Block: 1070931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123922 RingCT/type: yes/0
Extra: 01e778535b9a837dd8c6dcb8f7db7be7f397c4a5960ad9a2da6dfdb301dc91679a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3b195b5fac2044c86e4e0e6e90dbac49ee2f600d17d5d971eb6cabb8608b6c1 0.600000000000 1542966 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": 1070941, "vin": [ { "gen": { "height": 1070931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3b195b5fac2044c86e4e0e6e90dbac49ee2f600d17d5d971eb6cabb8608b6c1" } } ], "extra": [ 1, 231, 120, 83, 91, 154, 131, 125, 216, 198, 220, 184, 247, 219, 123, 231, 243, 151, 196, 165, 150, 10, 217, 162, 218, 109, 253, 179, 1, 220, 145, 103, 154, 2, 17, 0, 0, 0, 4, 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