Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a7e8f37542f81a4804ca70e524c4894bd30c6084a0794d89742e629fc402148

Tx prefix hash: 0a6ad1f2030a9a812c03b49ccba6ae4186398289a9afbf26c52ed6b096f6a67a
Tx public key: 1415a3a22bae0904ad04915874d69e6a61cfb94d128e3db39e145817588f49e9
Timestamp: 1709193810 Timestamp [UCT]: 2024-02-29 08:03:30 Age [y:d:h:m:s]: 00:361:18:23:04
Block: 967976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258647 RingCT/type: yes/0
Extra: 011415a3a22bae0904ad04915874d69e6a61cfb94d128e3db39e145817588f49e902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0968f5a58e4db8a2c7fae60a0e16a32c6cfa2180140f82dbeb0ad5722e36782 0.600000000000 1427771 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": 967986, "vin": [ { "gen": { "height": 967976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0968f5a58e4db8a2c7fae60a0e16a32c6cfa2180140f82dbeb0ad5722e36782" } } ], "extra": [ 1, 20, 21, 163, 162, 43, 174, 9, 4, 173, 4, 145, 88, 116, 214, 158, 106, 97, 207, 185, 77, 18, 142, 61, 179, 158, 20, 88, 23, 88, 143, 73, 233, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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