Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc417e5190469e129cbfd8d36f7773d9b40110b82a2d504dc9b054932fd14bc6

Tx prefix hash: ee9187e8026bab4e8be11842b717757a6d6d65dd08dec85d8df7b1d797d6e8d2
Tx public key: deb3bd23c7566ace36642759db8c4bb2c1e0ce8208d2d13ed22393b245fcd0f2
Timestamp: 1727910315 Timestamp [UCT]: 2024-10-02 23:05:15 Age [y:d:h:m:s]: 01:039:05:38:39
Block: 1123141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286418 RingCT/type: yes/0
Extra: 01deb3bd23c7566ace36642759db8c4bb2c1e0ce8208d2d13ed22393b245fcd0f2021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3974dc0708c17d196240e6d5db8e99fc38318272cec16458430999d53e7ef39b 0.600000000000 1605674 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": 1123151, "vin": [ { "gen": { "height": 1123141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3974dc0708c17d196240e6d5db8e99fc38318272cec16458430999d53e7ef39b" } } ], "extra": [ 1, 222, 179, 189, 35, 199, 86, 106, 206, 54, 100, 39, 89, 219, 140, 75, 178, 193, 224, 206, 130, 8, 210, 209, 62, 210, 35, 147, 178, 69, 252, 208, 242, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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