Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c627cdfa61560d773352b36d12f5e850969cb64e7eb105ee37da94d045a0bc7

Tx prefix hash: e6f9528b61fa06134a40bc34e58eb3a3aa455e6f011f0672cec359ce51b11a5c
Tx public key: 58d055c1b21138d4b2352df3d36d546f5a4246736f0ccfbb72fdf7bfb714efe8
Timestamp: 1720283366 Timestamp [UCT]: 2024-07-06 16:29:26 Age [y:d:h:m:s]: 00:271:09:13:33
Block: 1059905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193889 RingCT/type: yes/0
Extra: 0158d055c1b21138d4b2352df3d36d546f5a4246736f0ccfbb72fdf7bfb714efe802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3c07a804bf71f384b82f80e2d638491b0c841aff4934b86da36407cedbf2e47 0.600000000000 1530376 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": 1059915, "vin": [ { "gen": { "height": 1059905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3c07a804bf71f384b82f80e2d638491b0c841aff4934b86da36407cedbf2e47" } } ], "extra": [ 1, 88, 208, 85, 193, 178, 17, 56, 212, 178, 53, 45, 243, 211, 109, 84, 111, 90, 66, 70, 115, 111, 12, 207, 187, 114, 253, 247, 191, 183, 20, 239, 232, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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