Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f35e427d08601ec9a098ee419e12b787dfdd46e06a47d1c9b62dd352293246

Tx prefix hash: 274293ca21f20572a71e566e58bb7110f6c035414f59eefb31d02ebe8ff7fd8f
Tx public key: df25df612c69c9812bb746d46223f4aaa444ae19a7d5594cb4ea4940862c8ec7
Timestamp: 1711731503 Timestamp [UCT]: 2024-03-29 16:58:23 Age [y:d:h:m:s]: 00:300:05:41:07
Block: 989020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214844 RingCT/type: yes/0
Extra: 01df25df612c69c9812bb746d46223f4aaa444ae19a7d5594cb4ea4940862c8ec70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d66e3c790feba8a1a401b34d8a403049bd0d0c67c8620f7c42cca6410af5b20 0.600000000000 1449311 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": 989030, "vin": [ { "gen": { "height": 989020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d66e3c790feba8a1a401b34d8a403049bd0d0c67c8620f7c42cca6410af5b20" } } ], "extra": [ 1, 223, 37, 223, 97, 44, 105, 201, 129, 43, 183, 70, 212, 98, 35, 244, 170, 164, 68, 174, 25, 167, 213, 89, 76, 180, 234, 73, 64, 134, 44, 142, 199, 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