Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4da6eb8c7d6846d561a67bbcce1d0ddf6d761a2f860695a8db98c3f4a432598

Tx prefix hash: 1e7eb45ea927ec87562a61bed05cb38f3dfc01e46c9aa65e47a7b07e921480e7
Tx public key: ba359ca7dc55c236f4d4e7c50ebaaad873cf42cba1f6c80cb9050918d16c9ef2
Timestamp: 1709562992 Timestamp [UCT]: 2024-03-04 14:36:32 Age [y:d:h:m:s]: 01:260:17:55:22
Block: 971034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445083 RingCT/type: yes/0
Extra: 01ba359ca7dc55c236f4d4e7c50ebaaad873cf42cba1f6c80cb9050918d16c9ef20211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd67821fc8f5cbb4e5912e19749072293bea8d95280c85f072f4c091fb30aea0 0.600000000000 1430907 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": 971044, "vin": [ { "gen": { "height": 971034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd67821fc8f5cbb4e5912e19749072293bea8d95280c85f072f4c091fb30aea0" } } ], "extra": [ 1, 186, 53, 156, 167, 220, 85, 194, 54, 244, 212, 231, 197, 14, 186, 170, 216, 115, 207, 66, 203, 161, 246, 200, 12, 185, 5, 9, 24, 209, 108, 158, 242, 2, 17, 0, 0, 0, 6, 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