Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1f6f35639b840ab741f04e962fe9bb275c2d655e8f685ca4df1e94b02a7f368

Tx prefix hash: 4c9f04099b0fdd39769cf2ab494cad1b02a551193de4ddf55c3df6672c7469e4
Tx public key: 3d8c0ace9685e1ea53a4f2848fb3a3b0c4ce2408d60d352b22d5d7ca950e7e43
Timestamp: 1677078591 Timestamp [UCT]: 2023-02-22 15:09:51 Age [y:d:h:m:s]: 02:092:21:51:41
Block: 702598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588035 RingCT/type: yes/0
Extra: 013d8c0ace9685e1ea53a4f2848fb3a3b0c4ce2408d60d352b22d5d7ca950e7e4302110000000174b6d784000000000000000000

1 output(s) for total of 2.884038630000 dcy

stealth address amount amount idx
00: 10d53941de9feb2ba65ac8f784a0d337cd9eb0242ef0590edf204ad243831f10 2.884038630000 1146117 of 0

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": 702608, "vin": [ { "gen": { "height": 702598 } } ], "vout": [ { "amount": 2884038630, "target": { "key": "10d53941de9feb2ba65ac8f784a0d337cd9eb0242ef0590edf204ad243831f10" } } ], "extra": [ 1, 61, 140, 10, 206, 150, 133, 225, 234, 83, 164, 242, 132, 143, 179, 163, 176, 196, 206, 36, 8, 214, 13, 53, 43, 34, 213, 215, 202, 149, 14, 126, 67, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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