Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3afe2bfb68e0684aef55b5eda5fe4f1731c85ca7d1a387f1058330330e4b8d77

Tx prefix hash: 4fd2be07ef40a5f8585c8cdea86817d2bbab8b5f22471069258d15d7336a28bd
Tx public key: 52886899262665b59c51d51272c5f35d2904d743b4c1be63e8bdb1ad9750322c
Timestamp: 1722509879 Timestamp [UCT]: 2024-08-01 10:57:59 Age [y:d:h:m:s]: 00:259:07:48:06
Block: 1078364 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185229 RingCT/type: yes/0
Extra: 0152886899262665b59c51d51272c5f35d2904d743b4c1be63e8bdb1ad9750322c021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c92da2261a52ecee0074387293dd52cf859302b89494e8d08a7d8c6b413d02b 0.600000000000 1550941 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": 1078374, "vin": [ { "gen": { "height": 1078364 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c92da2261a52ecee0074387293dd52cf859302b89494e8d08a7d8c6b413d02b" } } ], "extra": [ 1, 82, 136, 104, 153, 38, 38, 101, 181, 156, 81, 213, 18, 114, 197, 243, 93, 41, 4, 215, 67, 180, 193, 190, 99, 232, 189, 177, 173, 151, 80, 50, 44, 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