Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 097d784db2aed17eaf26dfcb31b8bf6e49a882102c22c4c90979264f8bc6e551

Tx prefix hash: 01d3ca2c2908cd045f8c3a363b7f31d5319cedbb9f77f2b02344e870ad8c3c11
Tx public key: 7c6b3dd160770a241c78363e2bdbed1bbc4f812e2f27ea9d178d77709151702a
Timestamp: 1722737379 Timestamp [UCT]: 2024-08-04 02:09:39 Age [y:d:h:m:s]: 00:242:23:43:54
Block: 1080256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173541 RingCT/type: yes/0
Extra: 017c6b3dd160770a241c78363e2bdbed1bbc4f812e2f27ea9d178d77709151702a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d8ec14c59c7f7c5584405936cdd0488671a4cfe88f183596a3618dcb47a7d45 0.600000000000 1553541 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": 1080266, "vin": [ { "gen": { "height": 1080256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d8ec14c59c7f7c5584405936cdd0488671a4cfe88f183596a3618dcb47a7d45" } } ], "extra": [ 1, 124, 107, 61, 209, 96, 119, 10, 36, 28, 120, 54, 62, 43, 219, 237, 27, 188, 79, 129, 46, 47, 39, 234, 157, 23, 141, 119, 112, 145, 81, 112, 42, 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