Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db370d1d6461bbcc22cdf7a46b6d41ded6aad03b227895a376403d8f0e858d7d

Tx prefix hash: cf7e49b23c49ffe63c35782e2bba1875920b5354ce3eea360d9fb96dc452cb9e
Tx public key: 8f0f33c57bd854bcf9cc4d6a88bdcdd3dd780131a666d9acf1cb4a6ab2937a42
Timestamp: 1698738351 Timestamp [UCT]: 2023-10-31 07:45:51 Age [y:d:h:m:s]: 01:092:22:18:13
Block: 881490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327397 RingCT/type: yes/0
Extra: 018f0f33c57bd854bcf9cc4d6a88bdcdd3dd780131a666d9acf1cb4a6ab2937a4202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.736644103000 dcy

stealth address amount amount idx
00: 3c2ba540d7eb3d3147f0ab4b5e827e8b6529c206b0f9f3ae6eed624f610e8ef5 0.736644103000 1337080 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": 881500, "vin": [ { "gen": { "height": 881490 } } ], "vout": [ { "amount": 736644103, "target": { "key": "3c2ba540d7eb3d3147f0ab4b5e827e8b6529c206b0f9f3ae6eed624f610e8ef5" } } ], "extra": [ 1, 143, 15, 51, 197, 123, 216, 84, 188, 249, 204, 77, 106, 136, 189, 205, 211, 221, 120, 1, 49, 166, 102, 217, 172, 241, 203, 74, 106, 178, 147, 122, 66, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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