Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35f463b5bc8465c1ac14d1e63aaf7f239c752a4dc3b8208e8443a56bb1ec57aa

Tx prefix hash: a0e71950b6f1709fe1b3919e565a9c805c89a9126734eb656d4db528ced987a5
Tx public key: 194285cf2258da70aea47ef98023518d7da0a0cf3aa9db5c914881c8254c1ae2
Timestamp: 1714653905 Timestamp [UCT]: 2024-05-02 12:45:05 Age [y:d:h:m:s]: 00:322:01:57:40
Block: 1013240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230254 RingCT/type: yes/0
Extra: 01194285cf2258da70aea47ef98023518d7da0a0cf3aa9db5c914881c8254c1ae20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b30b99f1cace83a41aa413a866e7b6e205489f16ca7268a090918e858c911f20 0.600000000000 1476003 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": 1013250, "vin": [ { "gen": { "height": 1013240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b30b99f1cace83a41aa413a866e7b6e205489f16ca7268a090918e858c911f20" } } ], "extra": [ 1, 25, 66, 133, 207, 34, 88, 218, 112, 174, 164, 126, 249, 128, 35, 81, 141, 125, 160, 160, 207, 58, 169, 219, 92, 145, 72, 129, 200, 37, 76, 26, 226, 2, 17, 0, 0, 0, 1, 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