Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e4446b5900dac276caee11931de586266cf7cadb6ca91d9dc555b276af68efd

Tx prefix hash: 07381f3d17b3873ea46e73b8586770b3338b39ca8e73d2627f4e047dfa36350f
Tx public key: 43bcd5ed6cfdd59c0f415b1ea42657651c83ca5ba50086c3c67015a525904b95
Timestamp: 1709183262 Timestamp [UCT]: 2024-02-29 05:07:42 Age [y:d:h:m:s]: 01:026:06:16:03
Block: 967884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279750 RingCT/type: yes/0
Extra: 0143bcd5ed6cfdd59c0f415b1ea42657651c83ca5ba50086c3c67015a525904b950211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e707ed904d3f96f7f97b619563b1e945f8cf8d7899d43a742891a8b8a8508ad7 0.600000000000 1427675 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": 967894, "vin": [ { "gen": { "height": 967884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e707ed904d3f96f7f97b619563b1e945f8cf8d7899d43a742891a8b8a8508ad7" } } ], "extra": [ 1, 67, 188, 213, 237, 108, 253, 213, 156, 15, 65, 91, 30, 164, 38, 87, 101, 28, 131, 202, 91, 165, 0, 134, 195, 198, 112, 21, 165, 37, 144, 75, 149, 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