Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ff73b6ca7110cc139c7283806a06fdf457261c1339665367955753527a17b9

Tx prefix hash: 4f76b1bf1db871c9154fca9c1c55e5800a4a865f3462cbe5663515b9f730848c
Tx public key: 1ab346e85ce6137edc323e86b018a35bb8b9b5b82e5802f25f1cd2555aa7fa0c
Timestamp: 1714170034 Timestamp [UCT]: 2024-04-26 22:20:34 Age [y:d:h:m:s]: 00:349:00:47:50
Block: 1009216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249515 RingCT/type: yes/0
Extra: 011ab346e85ce6137edc323e86b018a35bb8b9b5b82e5802f25f1cd2555aa7fa0c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11f25ae9bcc055c53d5bd05b158f01b3c65fc4e00db33be48fb8191b5ab75514 0.600000000000 1470824 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": 1009226, "vin": [ { "gen": { "height": 1009216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11f25ae9bcc055c53d5bd05b158f01b3c65fc4e00db33be48fb8191b5ab75514" } } ], "extra": [ 1, 26, 179, 70, 232, 92, 230, 19, 126, 220, 50, 62, 134, 176, 24, 163, 91, 184, 185, 181, 184, 46, 88, 2, 242, 95, 28, 210, 85, 90, 167, 250, 12, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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