Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7336ba7936bb95a83210a7b42585914c7f8f92348b809b75a13f40e434b6a01e

Tx prefix hash: 4003a1e4acab04a278a3aad7951d735506d2c7ef6077f38f86937cbcf2b47c51
Tx public key: 21d522ceb32904216a89d720353a0056a5453cfb64c64ce4bdf9f8c8b565b688
Timestamp: 1714839240 Timestamp [UCT]: 2024-05-04 16:14:00 Age [y:d:h:m:s]: 00:250:03:49:56
Block: 1014781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179037 RingCT/type: yes/0
Extra: 0121d522ceb32904216a89d720353a0056a5453cfb64c64ce4bdf9f8c8b565b6880211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 839660ed0128f4e7d0bbdc80b45da2f102c2e2e4566e796cae1cecb714731299 0.600000000000 1477964 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": 1014791, "vin": [ { "gen": { "height": 1014781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "839660ed0128f4e7d0bbdc80b45da2f102c2e2e4566e796cae1cecb714731299" } } ], "extra": [ 1, 33, 213, 34, 206, 179, 41, 4, 33, 106, 137, 215, 32, 53, 58, 0, 86, 165, 69, 60, 251, 100, 198, 76, 228, 189, 249, 248, 200, 181, 101, 182, 136, 2, 17, 0, 0, 0, 3, 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