Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e661358d1d4ca56f0067c5b5bee22cd16dc8399ffe513dfb16454683a05ef57

Tx prefix hash: 42cba45a7d2298b867d43850d1d78d4e999422a5808f4420a67a0cd145490bfd
Tx public key: fe0378c503974e4dd95ec8962c3c20e80368abad889a5a5c0f2ad076f9c91a81
Timestamp: 1712330449 Timestamp [UCT]: 2024-04-05 15:20:49 Age [y:d:h:m:s]: 01:041:11:23:34
Block: 993946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290646 RingCT/type: yes/0
Extra: 01fe0378c503974e4dd95ec8962c3c20e80368abad889a5a5c0f2ad076f9c91a8102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c714ed1f8a9e9a1b9ed21e0fb7139db5fabfda2b8e9e5ce9ca55b86e5096f10e 0.600000000000 1454342 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": 993956, "vin": [ { "gen": { "height": 993946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c714ed1f8a9e9a1b9ed21e0fb7139db5fabfda2b8e9e5ce9ca55b86e5096f10e" } } ], "extra": [ 1, 254, 3, 120, 197, 3, 151, 78, 77, 217, 94, 200, 150, 44, 60, 32, 232, 3, 104, 171, 173, 136, 154, 90, 92, 15, 42, 208, 118, 249, 201, 26, 129, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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